Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [Workspace]Fix workspace detail classname definition #7986

Merged
merged 5 commits into from
Sep 4, 2024

Conversation

yubonluo
Copy link
Contributor

@yubonluo yubonluo commented Sep 4, 2024

Description

The previous code did not add a specific classname for [id^="row"][id$="expansion"], which resulted the SCSS file affecting the global UI. Therefore, add a specific classname to it so that it only takes effect in the table in the workspace details section.

Issues Resolved

Screenshot

Testing the changes

Changelog

  • fix: Fix workspace detail classname definition

Check List

  • All tests pass
    • yarn test:jest
    • yarn test:jest_integration
  • New functionality includes testing.
  • New functionality has been documented.
  • Update CHANGELOG.md
  • Commits are signed per the DCO using --signoff

Signed-off-by: yubonluo <yubonluo@amazon.com>
Signed-off-by: yubonluo <yubonluo@amazon.com>
Signed-off-by: yubonluo <yubonluo@amazon.com>
Copy link

codecov bot commented Sep 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.09%. Comparing base (7dedc58) to head (d2b2f03).
Report is 11 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7986   +/-   ##
=======================================
  Coverage   61.09%   61.09%           
=======================================
  Files        3691     3691           
  Lines       87310    87310           
  Branches    13433    13433           
=======================================
  Hits        53340    53340           
  Misses      30722    30722           
  Partials     3248     3248           
Flag Coverage Δ
Linux_1 29.32% <ø> (ø)
Linux_2 56.24% <ø> (ø)
Linux_3 37.93% <ø> (ø)
Linux_4 29.59% <ø> (ø)
Windows_1 29.34% <ø> (ø)
Windows_2 56.19% <ø> (ø)
Windows_3 37.94% <ø> (ø)
Windows_4 29.59% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a big issue, but what about applying BEM style css class name?

@ruanyl ruanyl merged commit 95929a6 into opensearch-project:main Sep 4, 2024
67 checks passed
@opensearch-trigger-bot
Copy link
Contributor

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.x
# Create a new branch
git switch --create backport/backport-7986-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 95929a6af6cc7171d4c5ddb8f2dccb307bd07e98
# Push it to GitHub
git push --set-upstream origin backport/backport-7986-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-7986-to-2.x.

paulstn added a commit to paulstn/OpenSearch-Dashboards that referenced this pull request Sep 4, 2024
opensearch-trigger-bot bot pushed a commit that referenced this pull request Sep 5, 2024
(cherry picked from commit 95929a6)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
ruanyl pushed a commit that referenced this pull request Sep 5, 2024
…8018)

(cherry picked from commit 95929a6)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
opensearch-trigger-bot bot pushed a commit that referenced this pull request Sep 6, 2024
…8018)

(cherry picked from commit 95929a6)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
(cherry picked from commit 67aa197)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
SuZhou-Joe pushed a commit that referenced this pull request Sep 6, 2024
…8018) (#8054)

(cherry picked from commit 95929a6)



(cherry picked from commit 67aa197)

Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants